Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated README with libyajl2 warning #121

Merged
merged 2 commits into from
Jul 19, 2023

Conversation

tpowell-progress
Copy link
Contributor

Description

omnibus image misbehaves (such as omnibus 3.0.0 built into chefes/omnibus-toolchain-windows-2019:3.0.0) because ffi-yajl 2.4 is already installed, which as cleaned up the build artifacts for libyajl2-gem causing the libyajldll.a to not be found on install of a second ffi-yajl version. Only seems to break on bundling, though.

Issues Resolved

Can repost #114 now under 2.6

Check List

Signed-off-by: Thomas Powell <thomas.powell@progress.com>
@tpowell-progress tpowell-progress added the Expeditor: Bump Version Minor Used by github.minor_bump_labels to bump the Minor version number. label Jul 19, 2023
Signed-off-by: Thomas Powell <thomas.powell@progress.com>
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@tpowell-progress tpowell-progress merged commit 4f2fb1b into main Jul 19, 2023
@tpowell-progress
Copy link
Contributor Author

@stanhu if you are interested in trying ffi-yajl 2.6, I've repushed now that I've been able to confirm that the new push was not the problem. Apologies for all of the confusion and delay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Expeditor: Bump Version Minor Used by github.minor_bump_labels to bump the Minor version number.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants